Welcome to another "Weekly Concerns". This is a post-a-week series of interesting links, relevant to programming and programmers. You can check out previous Weekly Concerns posts in the archive.

• Tainted Love as played on 13 noisy floppy and 1 hard disk drives.
• ConduitJS is a "targeted AOP" framework for JavaScript
• Couldn't get enough Pete last week, eh? He wrote another blog post about Parameter Checking with Postsharp
• Check out this book on the Mikado Method of refactoring. I'm not familiar with it yet, but looks interesting.
• Using RealProxy for AOP

If you have an interesting link that you'd like to see in Weekly Concerns, leave a comment or contact me.

Hello, again! "Weekly Concerns" is a post-a-week series of interesting links, relevant to programming and programmers. You can check out previous Weekly Concerns posts in the archive.

• Pete Shearer from the Pete on Software podcast kindly invited me to be on his show so I could shamelessly plug AOP in .NET:
  • Episode 5 of the Pete on Software podcast
  • AOP with Matthew Groves blog post, from Pete's blog.
  • Pete also did an Intro to AOP with PostSharp blog post.
• "Pete, Pete, Pete, enough about Pete already!" Okay, okay.
• I was reminded again recently how bad I am with regular expressions and how much I don't like them. Well, I came across a "fluent" interface for regular expressions called VerbalExpressions. I haven't used it yet, but it's something to keep an eye on.
• These sorts of questions aren't common on Stack Overflow anymore, but check out the answers for Strangest Language Feature. There are some answers that I found very cool and some that were real head-scratchers. Not a lot of C# answers in there; I guess C# isn't a very strange language :)
• Another tool to help remote pair programming: go-pty-screen

Welcome to Cross Cutting Concerns. "Weekly Concerns" is a post-a-week series of interesting links, relevant to programming and programmers. You can check out previous Weekly Concerns posts in the archive.

• On Helping Other People, from my colleague's blog Pete on Software. Just do it, stop with the excuses.
• The end of Windows XP support from Microsoft brings about an ominous deadline for ATM machines, reminiscent of Y2K.
• 3d printers are really starting to get interesting. Here's a giant 3d concrete printer that can build a house - in about 24 hours.
• Danica McKellar explains the basics of the base-2 (binary) number system in an episode of Math Bites (double clink!)
• If you're into mobile dev, check out the new book from Manning, Windows Phone 8 in Action.

With my expanded focus, I decided to bring back my weekly link collection under the "Weekly Concerns" banner. Once again, this is just an excuse to avoid the work of having to write a real post.

• "using you're type's good by Gary Bernhardt" - a lightning talk from CodeMash 2014. Not quite as good as Wat (from CodeMash 2012), but still a very good piece of entertainment for developers.
• A news report from 1981 about the internet. Did you know that in the future you may read your newspaper ON YOUR COMPUTER!? "We aren't going to lose a lot [of money]..." Oh, you poor fool.
• An article about refactoring that I think demonstrates "sawtooth code" well
• Some code on-screen in an episode of Airwolf had a bug in it. Why do I know this? Internet.
• I recently moved this site to Windows Azure. This is the first site on Azure I ever had to move out of the "free" plan (since I'm using a custom domain name). I find this calculator to be very helpful when estimating what I'll be paying.

Maybe this series will turn into an Every-Other-Weekly Concerns?

• The Ruby Rogues podcast discussed AOP in a recent episode (episode 46). It's a good idea to listen to the whole podcast for context, but they don't really start discussing AOP directly until about 28 minutes in.
• The proxy/decorator pattern gives some of the same benefits that AOP can give you. Derick Bailey blogged about using proxies and decorators in JavaScript.
• A couple of white papers for you:
• FeatureC++ and AOP - What's feature-oriented programming?
• AOP is Quantification and Obliviousness - "obliviousness" often has a negative connotation, but I believe AOP in a team setting on a properly architected application can free up developers to concentrate on adding business value without having function requirements slowing them down

That's it for this week. Have a great weekend.